DRAKHYSYS INFINITY TILESET WORKBENCH V4.6
AREA TRANSITIONS / ENTRANCES
=========================================

Purpose
-------
V4.6 adds a visual ARE V1.0 transition editor so normal area-to-area travel can be authored without a BCS script.

BG2 navigation model
--------------------
- SR.BMP controls where the party may walk.
- ARE Travel Regions are invisible exit polygons. Entering one changes area.
- ARE Entrances are named arrival points in the destination area.
- WED wall polygons remain optional for occlusion/cover/door geometry.

Typical connection
------------------
DR0001 -> DR0002:
1. Open DR0001.ARE and the DR0001 area image.
2. Draw an exit polygon on a walkable edge/door/portal.
3. Name it TO_DR0002.
4. Destination area: DR0002
5. Destination entrance: FROM_DR0001
6. Export DR0001.ARE back to override.

Then:
1. Open DR0002.ARE and its area image.
2. Choose PLACE ENTRANCE ON MAP.
3. Click a walkable arrival point.
4. Name it FROM_DR0001.
5. Export DR0002.ARE back to override.

For a two-way link, repeat in the opposite direction:
DR0002 exit TO_DR0001 -> DR0001 entrance FROM_DR0002.

Safety
------
- V4.6 does not rebuild unrelated ARE sections.
- Existing actors, containers, scripts, ambients, doors, animations, etc. remain byte-for-byte in place.
- Navigation export appends replacement region/entrance/vertex tables and updates only the corresponding ARE header offsets/counts.
- Existing non-travel regions are preserved.
- Existing original vertices are copied first so container/door vertex indexes stay valid.
- Export reparses the result immediately and refuses success if the navigation tables do not round-trip.

Recommended workflow
--------------------
1. Keep active maps in override.
2. Back up the working ARE before overwriting.
3. Paint/test SR.BMP collision first.
4. Add entrances on walkable cells.
5. Draw travel regions over walkable exit zones.
6. Test the connection in game.
7. Once stable, move finished map batches to a new custom BIF and register that BIF in chitin.key.

Important
---------
Destination area fields use the resource name without .ARE, for example DR0002.
Destination entrance names must match an Entrance record in the destination ARE.
